[Experimental Bot, please feedback here]

Fill In The Commit Message: This PR contains a Commit with an Empty Commit Message. Please fill in the Commit Message with the PR Summary.

NuttX PR Requirements Review

While the provided information is a good start, it does not fully meet the NuttX PR requirements. Here's a breakdown:

Strengths:

• Clear summary: The summary clearly explains the purpose of the change (new demo application), its functionality (Bluetooth data display), and potential use cases (real and dummy data scenarios).
• Testing information: You mentioned the target boards used for testing (ESP32-Sparrow, ESP32-devkitc) and provided context on a workaround implemented for advertising issues.

Areas for improvement:

• Missing details in Summary:
  • Functional part: Specify which part of the codebase is affected (e.g., apps/examples/bluetooth).
  • How it works (technical details): Briefly explain the implementation details, like which Bluetooth profiles are used, how data is transmitted/received.
  • Issue/PR references: Link any related issues or PRs (if applicable).
• Incomplete Impact assessment:
  • New feature: Clearly state that this is a new demo application.
  • User Impact: Describe how users can utilize this new application (e.g., building and flashing instructions, commands to run).
  • Build impact: Mention any new dependencies or build configuration changes required.
  • Documentation impact: Confirm if documentation is updated/provided to reflect this new application.
  • Other impacts: Address all other impact points (hardware, security, compatibility) even if they are not applicable ("N/A" is acceptable).
• Missing Testing logs: Provide actual testing logs (before and after the change) to demonstrate the application's functionality.

Recommendations:

1. Expand the Summary section with the missing technical details and references.
2. Thoroughly address all points in the Impact section, even if the impact is "NO" or "N/A".
3. Include actual testing logs demonstrating the application's behavior before and after your changes.

By providing this additional information, your PR will be more comprehensive and better aligned with NuttX requirements.

Very cool @robertc2000 !! :-) Could you please add some documentation too (https://github.com/apache/nuttx/tree/master/Documentation)? :-)

please fix the style issue report here:
https://github.com/apache/nuttx-apps/actions/runs/11580827866/job/32250505341?pr=2801

../nuttx/tools/checkpatch.sh -m -g d9e178aad022030224d1c95628cab1784a13a339..HEAD
/home/runner/work/nuttx-apps/nuttx-apps/apps/examples/ble/ble.c: error: No block comments found
Error: /home/runner/work/nuttx-apps/nuttx-apps/apps/examples/ble/ble.c:1:1: error: Missing file header comment block
Warning: /home/runner/work/nuttx-apps/nuttx-apps/apps/examples/ble/ble.c:1:1: warning: #include outside of 'Included Files' section
Error: /home/runner/work/nuttx-apps/nuttx-apps/apps/examples/ble/ble.c:2:0: error: Path relative to repository other than "nuttx" must begin with the root directory
Warning: /home/runner/work/nuttx-apps/nuttx-apps/apps/examples/ble/ble.c:2:1: warning: #include outside of 'Included Files' section

you can run this command locally before updating the patch:

../nuttx/tools/checkpatch.sh -g HEAD~...HEAD